← CSI Knowledge

26 — AI Agents and MCP

name
26 — AI Agents and MCP
source
Notion Export
migration_status
Imported
document_id
document_type
domain
hierarchy
status
version
owner
created
last_updated
review_date
review_priority
effective
next_review
languages
source_archive
source_formats
source_files
source_path
/home/csi/master/inbox/imports/notion-verify/staging/notion/Export-a01daa1a-664a-4975-9744-61a6104bc176/CSI Nexus тАФ Operating System/CSI AI Infrastructure & Business Automation Framew/26 тАФ AI Agents and MCP 3ab4d7783953816381ace2759c3c7f3e.md
classification_reason
Substantive AI architecture/reference document
imported_at
2026-08-12T01:17:17.625385
04-AI/26 — AI Agents and MCP.md

26 — AI Agents and MCP

Owner CSI Technology & Documentation Lead
Version 1.0
Status Under Review — CSI MCP Gateway v0.1.4, n8n and Telegram operations are technically validated; proactive alerting and extended pilot remain pending
Review frequency Quarterly and after material change
Applicable environments CSI Lab, Development, Testing, Staging, Production, Disaster Recovery, Client Site

Required coverage

Include:

  • AI agents
  • Tool calling
  • Agent memory
  • Short-term memory
  • Long-term memory
  • Planning
  • Task execution
  • Supervisor agent
  • Worker agents
  • Multi-agent systems
  • Human approval
  • Guardrails
  • Permissions
  • Sandboxing
  • Audit logs
  • Agent identity
  • Agent credentials
  • Agent limits
  • Error recovery
  • Agent monitoring
  • MCP clients
  • MCP servers
  • MCP tools
  • MCP resources
  • Local MCP
  • Cloud MCP
  • Security
  • Data access
  • Approval controls

Create:

  • Agent architecture
  • Agent permission matrix
  • Tool register
  • MCP server register
  • Agent testing checklist
  • Agent risk checklist

Acceptance rule

This chapter becomes Active only after accuracy review, command or workflow testing where applicable, risk review, owner assignment, approval, and change-history entry.

CSI MCP Gateway — official reference order

  1. Build, deployment, operations and recovery: CSI-RUN-MCP-001 — CSI MCP Gateway v0.1.4 Build, Deployment & Recovery Runbook
  2. Source files, configuration and dependency lock: CSI-MCP-FILE-001 — CSI MCP Gateway v0.1.4 Source Files & Configuration Register
  3. Validation evidence, known errors and pilot record: CSI-MCP-VAL-001 — Live Validation, Troubleshooting & Pilot Record — 2026-07-28

Current verified endpoint: https://mcp.cyberspaceinfocom.com/mcp

Current verified health endpoint: https://mcp.cyberspaceinfocom.com/healthz

Current verified release: 0.1.4

Change history

Date Version Change
28 July 2026 1.0 Initial chapter brief created from the master framework.
28 July 2026 1.1 Added the verified CSI MCP Gateway v0.1.3 runbook, source-file register, validation evidence and future-support reference order.

CSI-RUN-MCP-001 — CSI MCP Gateway v0.1.4 Build, Deployment & Recovery Runbook

CSI-MCP-FILE-001 — CSI MCP Gateway v0.1.4 Source Files & Configuration Register

CSI-MCP-VAL-001 — Live Validation, Troubleshooting & Pilot Record — 2026-07-28

CSI-RUN-MCP-N8N-001 — n8n ↔ CSI MCP Gateway v0.1.4 Integration Runbook

Verified n8n integration — 29 July 2026

  1. n8n integration, monitoring extension and recovery: CSI-RUN-MCP-N8N-001 — n8n ↔ CSI MCP Gateway v0.1.4 Integration Runbook

Current verified release: 0.1.4

Current verified automated tests: 6 files; 18 tests passed.

Current direct ChatGPT constraint: custom MCP app availability depends on eligible ChatGPT workspace entitlement.

Telegram operations channel and monitoring expansion — 29 July 2026

Current verified targets: Linux server, OPNsense, Grafana, Nextcloud, n8n, MCP Gateway, Prometheus, Blackbox Exporter and Nginx Proxy Manager.

Security boundaries remain unchanged: no Docker socket in MCP, no shell tool, explicit service allow-list, encrypted n8n credentials and read-only MCP operations.

Next automation sequence

  1. Completed: exact /status and approved operator Chat-ID gate; unrelated messages are silently ignored.
  2. Next: build service-down plus recovery alerts with duplicate suppression.
  3. Build daily scheduled health summary.
  4. Add ERPNext, Portainer, Homepage and RustDesk monitoring.
  5. Add database, Redis, queue and runner health.
  6. Complete seven-day pilot and rollback drill.
  7. Begin n8n AI Agent integration only after monitoring controls stabilize.
  8. Defer voice control until AI-agent authorization and approval controls are validated.

Detailed evidence and procedures: CSI-RUN-MCP-N8N-001 — n8n ↔ CSI MCP Gateway v0.1.4 Integration Runbook

Operational status update — 3 August 2026

  • [x] CSI MCP Gateway deployed and healthy
  • [x] Authenticated n8n-to-MCP call validated
  • [x] Telegram status workflow published
  • [x] Approved operator gate validated
  • [x] Blackbox probe data included in the service-health path
  • [x] Read-only security boundaries preserved
  • [ ] Proactive alert/recovery automation
  • [ ] Seven-day pilot
  • [ ] Client-impacting agent actions; prohibited until a separate approval and liability framework is approved

The CSI operating policy remains: agents may assist, analyse and report, but must not make uncontrolled changes inside client infrastructure.